Support for line breaks between KML coordinate tuples #80
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
phayes
added a commit
that referenced
this pull request
Jul 16, 2013
Support for line breaks between KML coordinate tuples
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was trying to parse some KML files with geoPHP today and it kept throwing exceptions because the coordinate tuples in a LineString were separated with line breaks, not spaces. Google's KML reference says to use spaces, but they also provide examples where line breaks are used (see https://developers.google.com/kml/documentation/kml_tut#paths).
This might not be a legitimate issue, but I figured I'd send it in since almost every sample KML file out there seems to use line breaks.